Storage device for interfacing with host and method of operating the host and the storage device

ABSTRACT

A method of operating a storage device includes receiving, from a host, a first packet containing a buffer address indicating a location of a data buffer selected from among a plurality of data buffers in the host, parsing the buffer address from the first packet, and transmitting a second packet containing the buffer address to the host in response to the first packet.

CROSS-REFERENCE TO RELATED APPLICATION

This is a Continuation of U.S. application Ser. No. 17/359,864, filedJun. 28, 2021, which is a Continuation of U.S. application Ser. No.16/801,267, filed Feb. 26, 2020, which is a Continuation of U.S.application Ser. No. 15/961,920, filed Apr. 25, 2018, which claims thebenefit of Korean Patent Application No. 10-2017-0097133, filed on Jul.31, 2017, in the Korean Intellectual Property Office, the disclosure ofwhich is incorporated herein in its entirety by reference.

BACKGROUND

The disclosure relates to a method of operating a host and a storagedevice, and more particularly, to a storage device for interfacing witha host and a method of operating the host and the storage device.

A non-volatile memory device can retain data stored therein even whenpower is cut off. Recently, storage devices, such as an embeddedmulti-media card (eMMC), a universal flash storage (UFS), a solid-statedrive (SSD), and a memory card, which include flash-based non-volatilememory, have been widely used. Storage devices are useful for storing ormoving a large amount of data.

A data processing system including a storage device may be called astorage system. A storage system may include a host and a storagedevice. The host and the storage device may be connected through variousinterface standards and need to be improved with respect to dataprocessing performance by reducing overhead of data processingoperations, such as a read operation and a write operation, duringinterfacing.

SUMMARY

The disclosure provides a method of operating a host and a storagedevice to increase data processing performance by reducing overhead ofdata processing between the host and the storage device.

According to an aspect of the disclosure, there is provided a method ofoperating a storage device. The method includes receiving, from a host,a first packet including a buffer address indicating a location of adata buffer selected from among a plurality of data buffers in the host.The buffer address is parsed from the first packet. A second packetincluding the buffer address is transmitted to the host in response tothe first packet.

According to another aspect of the disclosure, there is provided astorage device having a memory core and a storage controller. The memorycore is configured to store data in a non-volatile manner. The storagecontroller is configured to interface with a host outside, to managebuffer addresses for a plurality of data buffers comprised in the host,to include a buffer address indicating a location of at least one databuffer in a packet, and to transmit the packet to the host when thepacket is for requesting access to the at least one data buffer.

According to another aspect of the disclosure, there is provided amethod of operating a host. The method includes receiving a first packetfrom a storage device, the first packet containing a first bufferaddress indicating a location of a data buffer selected from among aplurality of data buffers in the host. The first buffer address isparsed from the first packet. And data in a data buffer is accessed at alocation indicated by the first buffer address which has been parsed.

According to another aspect of the disclosure, there is provided amethod executed by a host for communicating with a nonvolatile memorydevice. The method includes receiving, from the nonvolatile memorydevice, a first packet comprising first information for identifying afirst address within a data buffer. In response to receiving the firstpacket, the first address is accessed using the first information.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings in which:

FIG. 1 is a block diagram of a data processing system according to anembodiment of the disclosure;

FIG. 2 is a block diagram of a host illustrated in FIG. 1 , according toan embodiment of the disclosure;

FIG. 3 is a block diagram of a storage controller illustrated in FIG. 1, according to an embodiment of the disclosure;

FIG. 4 is a block diagram of a storage system using a universal flashstorage (UFS) interface, according to an embodiment of the disclosure;

FIGS. 5 and 6 are flowcharts of a method of operating a host, accordingto an embodiment of the disclosure;

FIG. 7 is a flowchart of a method of operating a storage device,according to an embodiment of the disclosure;

FIG. 8 and FIGS. 9A and 9B are block diagrams of various kinds ofinformation stored in a host memory and a register included in a hostcontroller, according to an embodiment of the disclosure;

FIG. 10 and FIGS. 11A and 11B are diagrams of a data read operation andpackets involved in a UFS interface, according to an embodiment of thedisclosure;

FIGS. 12 and 13 are diagrams of a data write operation and packetsinvolved in the UFS interface, according to an embodiment of thedisclosure;

FIG. 14 is a diagram of an example in which an embodiment of thedisclosure is applied to various types of packets defined in the UFSinterface;

FIG. 15 is a block diagram of a storage controller managing a bufferaddress, according to an embodiment of the disclosure;

FIG. 16 is a flowchart of a method of operating the storage controllerillustrated in FIG. 15 , according to an embodiment of the disclosure;

FIGS. 17A through 17C are block diagrams of the operation of a storagesystem when a plurality of ready-to-transfer (RTT) UFS protocolinformation units (UPIUs) are transmitted in response to a singlecommand UPIU;

FIG. 18A shows a first type packet containing a buffer address,according to an embodiment of the disclosure;

FIG. 18B shows a second type packet that does not contain a bufferaddress, according to an embodiment of the disclosure;

FIG. 19 illustrates a command (CMD) UPIU for a data write operationaccording to an embodiment of the disclosure;

FIG. 20A shows an example of an RTT UPIU corresponding to the CMD UPIUshown in FIG. 19 according to an embodiment of the disclosure;

FIG. 20B shows another example of an RTT UPIU corresponding to the CMDUPIU shown in FIG. 19 according to another embodiment of the disclosure;

FIG. 21A shows another example of an RTT UPIU corresponding to the CMDUPIU shown in FIG. 19 , according to another embodiment of thedisclosure;

FIG. 21B shows another example of an RTT UPIU corresponding to the CMDUPIU shown in FIG. 19 , according to another embodiment of thedisclosure;

FIG. 22 shows an example in which an extra header segment (EHS) fieldincluded in a CMD UPIU may include an EHS header and an EHS dataaccording to an embodiment of the disclosure;

FIG. 23A shows an RTT UPIU transmitted by a storage device according toan embodiment of the disclosure;

FIG. 23B shows an RTT UPIU transmitted by a storage device according toanother embodiment of the disclosure;

FIG. 24 shows an RTT UPIU containing first through fourth bufferaddresses according to another embodiment of the disclosure; and

FIG. 25 shows an example of a UPIU according to another embodiment ofthe disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

FIG. 1 is a block diagram of a data processing system according to anembodiment of the disclosure.

A data processing system 10 may include a host 100 and a storage device200. The storage device 200 may include a storage controller 210 and amemory core 220. When the storage device 200 stores data in anon-volatile manner, the memory core 220 may include a non-volatilememory (NVM) core. The host 100 may include a host controller 110 and ahost memory 120. The host memory 120 may include a buffer area 121.

The data processing system (or storage system) 10 may be implemented asa personal computer (PC), a data server, a network-attached storage(NAS), an internet of things (IoT), or a portable electronic device. Theportable electronic device may be a laptop computer, a cellular phone, asmart phone, a tablet PC, a personal digital assistant (PDA), anenterprise digital assistant (EDA), a digital still camera, a digitalvideo camera, an audio device, a portable multimedia player (PMP), apersonal navigation device (PND), an MP3 player, a handheld gameconsole, an e-book, or a wearable device.

The storage device 200 may include storage media which store dataaccording to a request from the host 100. For example, the storagedevice 200 may include at least one solid state drive (SSD). When thestorage device 200 includes an SSD, the storage device 200 may include aplurality of flash memory chips (e.g., NAND memory chips) storing datain a non-volatile manner.

Alternatively, the storage device 200 may be a flash memory deviceincluding at least one flash memory chip. In some embodiments, thestorage device 200 may be an embedded memory in the storage system 10.For example, the storage device 200 may be an embedded multi-media card(eMMC) or an embedded universal flash storage (UFS) memory device. Inother embodiments, the storage device 200 may be an external memoryattachable to or detachable from the storage system 10. For example, thestorage device 200 may be a UFS memory card, a compact flash (CF) card,a secure digital (SD) card, a micro-SD card, a mini-SD card, an extremedigital (xD) card, or a memory stick.

When the storage device 200 includes flash memory, the flash memory mayinclude a two-dimensional (2D) NAND memory array or a three-dimensional(3D) (or vertical NAND (VNAND)) memory array. A 3D memory array may bemonolithically formed at at least one physical level of memory cellarrays, which have an active region disposed on a silicon substrate, orof a circuit, which is involved in the operation of memory cells andformed on or in the substrate. The term “monolithic” means that layersof each level of an array are directly deposited on layers of anunderlying level of the array. In some embodiments of the disclosure,the 3D memory array includes vertical NAND strings which are arranged ina vertical direction so that at least one memory cell is placed onanother memory cell. The at least one memory cell may include a chargetrap layer.

Structures of a 3D memory array, in which the 3D memory array includes aplurality of levels and word lines and/or bit lines that are shared bylevels, are disclosed in U.S. Pat. Nos. 7,679,133, 8,553,466, 8,654,587,8,559,235, and U.S. Patent Application No. 2011/0233648, the disclosuresof which are incorporated herein by references.

In another example, the storage device 200 may include different kindsof non-volatile memory. The storage device 200 may use magnetic randomaccess memory (MRAM), spin-transfer torque MRAM, conductive bridging RAM(CBRAM), ferroelectric RAM (FeRAM), phase RAM (PRAM), resistive RAM, andother different kinds of memory.

The host 100 may communicate with the storage device 200 using variouskinds of interfaces. For example, the host 100 may be connected with thestorage device 200 using a standard interface such as universal flashstorage (UFS), serial advanced technology attachment (SATA), smallcomputer small interface (SCSI), serial attached SCSI (SAS), or eMMC.The host 100 and the storage device 200 may generate and transmit apacket according to a protocol of the currently used interface. FIG. 1shows a first packet Packet_H generated in the host 100 and transmittedto the storage device 200 and a second packet Packet_S generated in thestorage device 200 and transmitted to the host 100.

The host controller 110 may include a host controller interface (notshown). The host controller interface may manage an operation of storingdata (e.g., write data) of the buffer area 121 in the memory core 220 orstoring data (e.g., read data) of the memory core 220 in the buffer area121. The storage controller 210 may include a device controllerinterface (not shown) for an interface with the host controller 110.

The host controller 110 and the host memory 120 may be implemented inseparate semiconductor chips, respectively. Alternatively, the hostcontroller 110 and the host memory 120 may be integrated into onesemiconductor chip. The host controller 110 may be one of a plurality ofmodules included in an application processor. The application processormay be implemented as a system on chip (SoC). The host memory 120 may bean embedded memory placed inside the application processor or a memorydevice or module placed outside the application processor.

The host 100 may also include various devices involved in the driving ofthe storage device 200. For example, a software module (not shown) suchas a host application or a device driver may be included in the host100. The software module may be loaded to the host memory 120 andexecuted by a processor (not shown).

The buffer area 121 of the host memory 120 may include a plurality ofdata buffers. The data buffers may be accessed by a buffer addressADD_Buf. For example, write data may be stored in a data buffer and maybe transmitted from the data buffer to the storage device 200 based onthe control of the host controller 110. In addition, read data from thestorage device 200 may be stored in a data buffer based on the controlof the host controller 110.

The host controller 110 may include the buffer address ADD_Buf, whichindicates a location of a data buffer selected from among a plurality ofdata buffers in response to a request, in the first packet Packet_H. Forexample, when the first packet Packet_H requesting a data write isgenerated, the host controller 110 may generate the first packetPacket_H containing the buffer address ADD_Buf indicating a location ofa data buffer in which write data has been stored and may transmit thefirst packet Packet_H to the storage device 200. When the first packetPacket_H requesting a data read is generated, the host controller 110may generate the first packet Packet_H containing the buffer addressADD_Buf indicating a location of a data buffer in which read data willbe stored.

The storage controller 210 may store and manage the buffer addressADD_Buf and a command parsed from the first packet Packet_H. Inaddition, when generating the second packet Packet_S in response to thefirst packet Packet_H, the storage controller 210 may include the bufferaddress ADD_Buf, which has been stored and managed in the storage device200, in the second packet Packet_S.

The host 100 may receive the second packet Packet_S, which contains thebuffer address ADD_Buf, from the storage controller 210 and may accessthe buffer area 121 using the buffer address ADD_Buf parsed from thesecond packet Packet_S. In other words, the host 100 does not need toaccess other areas to check relevant information in order to determine alocation of a data buffer but may access just a data buffercorresponding to the buffer address ADD_Buf parsed from the secondpacket Packet_S.

According to the embodiments described above, additional accessoperations of the host memory 120 are not necessary to determine alocation of a data buffer, and therefore, a frequency at which the hostcontroller 110 accesses the host memory 120 may be reduced. For example,conventionally, a buffer address is separately stored in one area withinthe host memory 120 and a separate access, i.e., an operation of readingthe buffer address needs to be performed in order to determine alocation of a data buffer in which write data has been stored or readdata will be stored. However, according to the embodiments of thedisclosure, the data buffer may be directly accessed without theseparate access operation. As a result, overhead of a data processingoperation is reduced, so that data processing performance is increased.

FIG. 2 is a block diagram of the host 100 illustrated in FIG. 1 ,according to an embodiment of the disclosure. FIG. 2 shows anapplication processor (AP) including a host controller.

Referring to FIG. 2 , the host 100 may include the AP and the hostmemory 120. The AP may include at least one module as an intellectualproperty (IP). For example, the AP may include the host controller 110,a processor 130, a modem 140, a camera interface (I/F) 150, a displayI/F 160, a memory control unit 171, and an embedded memory 172.

Although it is illustrated in FIG. 2 that the host memory 120 is anexternal memory of the AP, the disclosure is not limited thereto. Forexample, the embedded memory 172 of the AP may be used as a host memory.The elements shown in FIG. 2 are just examples and the AP may alsoinclude other elements than those shown in FIG. 2 or some of theelements shown in FIG. 2 may not be included in the AP.

The processor 130 may control all operations of the AP. For example,software (e.g., an AP and a device driver) for managing a datawrite/read operation on a storage device 200 may be loaded to the hostmemory 120 or the embedded memory 172, and the processor 130 may managethe data write/read operation by executing the software. The host memory120 may be implemented as volatile memory or non-volatile memory. Insome embodiments, the host memory 120 may include volatile memory suchas dynamic RAM (DRAM) and/or static RAM (SRAM).

The AP may perform a camera control operation, a display controloperation, and a modem operation. As the modem 140 is included in theAP, the AP may be referred to as a ModAP.

The host controller 110 may transmit or receive a packet containing thebuffer address ADD_Buf to or from the storage device 200, as describedabove. The host controller 110 may include a register 111 storing atleast one transfer request. Transfer requests involved in a writeoperation and/or a read operation on the storage device 200 may bestored in the register 111 based on the control of the processor 130.Various kinds of information used to generate a packet corresponding tothe transfer requests may be stored in the host memory 120 based on thecontrol of the processor 130. For example, table information includinginformation about the type of packet and the buffer address ADD_Buf maybe stored in the host memory 120. In case of a data write request, writedata may be stored in a plurality of data buffers in the host memory 120based on the control of the processor 130. The host controller 110 maycheck transfer requests stored in the register 111 and may interfacewith the storage device 200 based on the transfer requests.

As described above, the host controller 110 may receive a packetcontaining the buffer address ADD_Buf from the storage device 200, mayparse the buffer address ADD_Buf from the packet, and may determine alocation of a data buffer according to the buffer address ADD_Buf. Forexample, the host controller 110 may have lower access priority to thehost memory 120 than the other modules in the AP. In this case, latencytaken for the host controller 110 to access the host memory 120 may behigh. However, according to the embodiments of the disclosure, afrequency at which the host controller 110 accesses the host memory 120may be reduced and an increase in overhead of data processing operationsmay be prevented.

FIG. 3 is a block diagram of the storage controller 210 illustrated inFIG. 1 , according to an embodiment of the disclosure.

Referring to FIGS. 1 and 3 , the storage controller 210 may include acentral processing unit (CPU) 211 as a processor, a host I/F 212, and amemory I/F 213. The storage controller 210 may also include a flashtranslation layer (FTL) 214, a packet manager 215, and a buffer manager216. The storage controller 210 may also include a working memory (notshown) to which the FTL 214 is loaded and, as the CPU 211 executes theFTL 214, data write and read operations on a memory core 220 may becontrolled.

The host I/F 212 may transmit or receive a packet to or from the host100. As described above, the packet transmitted or received by the hostI/F 212 may contain the buffer address ADD_Buf indicating a location ofa data buffer in the buffer area 121 within the host 100. The memory I/F213 may perform an operation of writing or reading data by interfacingwith the memory core 220.

The packet manager 215 may generate a packet complying with the protocolof the interface between the packet manager 215 and the host 100 and mayparse various kinds of information from the packet. The buffer manager216 may manage an operation of storing the various kinds of informationparsed from the packet in a buffer 230. For example, the buffer manager216 may manage an operation of storing a command CMD and the bufferaddress ADD_Buf which have been parsed from the packet. The buffermanager 216 may also manage an operation of storing write data parsedfrom the packet in the buffer 230 and an operation of storing data readfrom the memory core 220 in the buffer 230. The buffer 230 may beincluded in the storage controller 210 or may be placed outside thestorage controller 210. Although the buffer address ADD_Buf and the dataare stored in one buffer in the embodiment illustrated in FIG. 3 , thebuffer address ADD_Buf and the data may be respectively stored inseparate storage circuits.

As described above, when the storage device 200 generates a packet to betransmitted to the host 100, the storage device 200 may read the bufferaddress ADD_Buf from the buffer 230 and may include the buffer addressADD_Buf in the packet to be transmitted to the host 100.

For example, in a data write operation, a write command and a firstbuffer address corresponding thereto may be parsed from a packetreceived from the host 100 and the first buffer address may be stored inthe buffer 230 of the storage device 200. The storage device 200 maygenerate a packet requesting to transfer write data in a predeterminedunit of size in response to the write command. At this time, the firstbuffer address corresponding to the write command may be included in thepacket and the host 100 may refer to the first buffer address containedin the packet and transmit the write data stored in a data buffer at alocation indicated by the first buffer address to the storage device200.

Similarly, in a data read operation, a read command and a second bufferaddress corresponding thereto may be parsed from a packet received fromthe host 100 and the second buffer address may be stored in the buffer230 of the storage device 200. The storage device 200 may generate apacket including read data in response to the read command. The secondbuffer address corresponding to the read command may be included in thepacket. The host 100 may refer to the second buffer address contained inthe packet and store the read data in a data buffer at a locationindicated by the second buffer address.

FIG. 4 is a block diagram of a storage system using a UFS interfaceaccording to an embodiment of the disclosure.

Referring to FIG. 4 , a UFS host and a UFS storage device may performcommunication according to a UFS interface in a storage system 300. TheUFS host may include a software module 310 and a hardware module whichincludes a UFS host controller 320 and a host memory 330. The softwaremodule 310 may include application software and a UFS host controllerdriver. The application software may be various application programsexecuted in the UFS host. The UFS host controller driver is used tomanage the driving of peripheral devices connected to the UFS host. Datamanagement operations such as data write and read operations on thestorage device may be performed by executing the UFS host controllerdriver. The application software and the UFS host controller driver maybe loaded to the host memory 330 shown in FIG. 4 or to another operatingmemory in the UFS host and may be executed by a processor.

The UFS host controller 320 may include a UFS host controller interface,a UFS transport protocol (UTP) engine, and a UFS interconnect layer. TheUFS host controller interface may receive a request generated using theUFS host controller driver and transmit the request to the UTP engine.The UFS host controller interface may also transmit a data access resultfrom the UTP engine to the UFS host controller driver. The UTP enginemay provide services for an upper layer (or application layer). The UTPengine may generate a packet or release a packet and parse informationtherein.

The UFS interconnect layer may communicate with a UFS storage device340. The UFS interconnect layer may include a link layer and a physical(PHY) layer. The link layer may be mobile industry processor interface(MIPI) UniPro and the PHY layer may be MIPI M-PHY. The UFS host mayprovide a reference clock Ref Clock and a reset signal Reset for the UFSstorage device 340 according to the UFS interface.

The UFS storage device 340 may include a storage controller and a memorycore. In the embodiment illustrated in FIG. 4 , the storage controllermay include a UFS interconnect layer, a UTP engine, and a UFS storagedevice interface. The memory core may be a core including non-volatilememory, i.e., an NVM core.

In the structure in which the UFS host controller 320 communicates withthe UFS storage device 340, transmitting or receiving data according toa request from the UFS host controller driver may be performed throughthe UFS host controller interface. For example, in a data writeoperation, the software module 310 may store write data in a data bufferof the host memory 330, the UFS host controller interface may access thedata buffer of the host memory 330, and the accessed write data may betransmitted to the UFS storage device 340.

According to an embodiment of the disclosure, a buffer addressindicating a location of a data buffer in the host memory 330 may beincluded in the first packet Packet_H transmitted from the UFS host tothe UFS storage device 340 and/or the second packet Packet_S transmittedfrom the UFS storage device 340 to the UFS host. The buffer address maycorrespond to a physical address indicating the location of the databuffer. Table information (e.g., a physical region description table(PRDT)) including buffer addresses may be stored in a certain area inthe host memory 330. The UTP engine of the UFS host may determine abuffer address based on the PRDT and generate the first packet Packet_Hcontaining the buffer address. The UTP engine of the UFS storage device340 may generate the second packet Packet_S containing a buffer addresswhich has been stored and managed in the UFS storage device 340.

The UFS host controller 320 may be connected with the UFS storage device340 by way of port-mapped input/output (I/O). Write and read operationsmay be processed in multi-task mode. Accordingly, the UFS storage device340 may store and manage a plurality of commands parsed from a pluralityof packets and buffer addresses corresponding to the commands.

As the UFS interface is used, various types of packets may be definedand embodiments of the disclosure may be applied to at least some ofthese packets. For example, a packet complying with the UFS interfacemay be defined as a UFS protocol information unit (UPIU). Various typesof packets may include a command UPIU for requesting to write or read, aresponse UPIU, a data_in UPIU including read data, a data_out UPIUincluding write data, a task management (TM) request UPIU, and aready-to-transfer (RTT) UPIU. According to embodiments of thedisclosure, the above-described buffer address may be included in atleast some types of packets among the various types of packets definedin the UFS interface. For example, the buffer address may be included ina packet request to access a data buffer of the host memory 330.

Hereinafter, the operations of an interface between a host and a storagedevice according to some embodiments of the disclosure will be describedin detail. Although the host and the storage device use the UFSinterface in these embodiments, the embodiments may also be applied toother kinds of interfaces than the UFS interface.

FIGS. 5 and 6 are flowcharts of a method of operating a host accordingto an embodiment of the disclosure. FIG. 5 shows an example where thehost transmits a packet. FIG. 6 shows an example where the host receivesa packet.

Referring to FIG. 5 , the host may include a host controller and variouskinds of information generated using a software module in the host maybe stored in a host memory. For example, at least one transfer requestmay be stored in a register within the host controller and a transferrequest descriptor corresponding to the transfer request may be storedin a certain region (e.g., a descriptor region) within the host memory.The transfer request descriptor may be used to generate a response UPIUand a command UPIU to be used together with PRDT information.Packet-related information such as a command UPIU or a response UPIU andPRDT information may be stored in another area within the host memory.The PRDT information may include a buffer address indicating a locationof a data buffer in which write data has been stored or read data willbe stored. The packet-related information stored in the host memory willbe referred to as command UPIU information or response UPIU information.

When a host controller interface operation is started for datatransmission/reception, the host controller may check a transfer requestdescriptor, which corresponds to the transfer request stored in theregister, in the host memory in operation S11. The host controller maycheck command UPIU information for a data write request and PRDTinformation using the transfer request descriptor in operation S12. Thehost controller may generate a packet containing a buffer address (e.g.,a physical address), which indicates a location of a data buffer inwhich write data has been stored, using the PRDT information inoperation S13 and may transmit the packet to a storage device inoperation S14.

Referring to FIG. 6 , the host may receive a packet from a storagedevice in operation S21. The packet may be provided for the hostcontroller within the host. The host controller may parse various kindsof information from the packet. As described above, the storage devicemay store and manage a command and a buffer address corresponding to thecommand, which have been transmitted from the host, and the bufferaddress may be included in at least some of various types of packetstransmitted from the storage device.

The host controller may parse a buffer address from the packet inoperation S22. The host controller may also access a data buffer withinthe host memory using the buffer address in operation S23. When thepacket corresponds to an RTT UPIU requesting to transfer write data, thehost controller may transmit write data stored in the data buffer at alocation corresponding to the buffer address to the storage device,without separately checking PRDT information stored in the host memory.When the packet corresponds to a data_in UPIU including read data, thehost controller may store the read data included in the packet in thedata buffer at the location corresponding to the buffer address, withoutseparately checking the PRDT information stored in the host memory.

FIG. 7 is a flowchart of a method of operating a storage deviceaccording to an embodiment of the disclosure.

The storage device may receive a first packet from a host in operationS31. The first packet may correspond to a command UPIU. The command UPIUmay include a command for a data access such as a data write or a dataread. As described above, the first packet may contain a buffer addressindicating a location of a data buffer in which write data has beenstored or read data will be stored. The storage device may parse thebuffer address from the first packet in operation S32 and may store andmanage the command contained in the first packet and the buffer addressin an internal storage circuit (e.g., a command queue and an addressqueue) in operation S33.

The storage device may generate a second packet in response to the firstpacket and transmit the second packet to the host. The buffer addressparsed from the first packet may be included in the second packetgenerated in response to the first packet in operation S34. For example,during a data write operation, the storage device may generate, as thesecond packet, an RTT UPIU indicating that it is ready to receive writedata and the buffer address may be included in the RTT UPIU. During adata read operation, the storage device may generate, as the secondpacket, a data_in UPIU including read data and the buffer address may beincluded in the data_in UPIU. The storage device may transmit the secondpacket containing the buffer address to the host in operation S35.

FIG. 8 and FIGS. 9A and 9B are block diagrams of various kinds ofinformation stored in a host memory and a register included in a hostcontroller, according to an embodiment of the disclosure.

Referring to FIG. 8 , a host 400 may include a host memory 410 and aregister 420. The register 420 may be provided inside a host controllerand the host memory 410 may be disposed outside the host controller.Various kinds of commands and parameters defined in Joint ElectronDevice Engineering Council (JEDEC) UFS standards may be stored in thehost memory 410 and the register 420 to manage data with respect to astorage device. A UTP transfer request descriptor may be stored in adescriptor region of the host memory 410 and UPIU information andcorresponding PRDT information may be stored in another region of thehost memory 410. UTP transfer request descriptors may be stored orchecked in the host memory 410 based on a UTP transfer request stored inthe register 420.

Write data and read data may be stored in a plurality of data buffersincluded in a buffer area of the host memory 410. PRDT information maycontain a buffer address as a physical address of a data buffer. PRDTinformation may not be stored with respect to some command UPIUs. Forexample, PRDT information may not be stored with respect to a commandUPIU irrelevant to an access to a data buffer.

Other various kinds of information defined in the JEDEC UFS standardsare illustrated in FIG. 8 . For example, a UTP task management requestlist may also be stored in one region of the host memory 410. Forinstance, a task management request UPIU and a task management responseUPIU may be stored in one region of the host memory 410. The taskmanagement request list may be stored in the host memory 410 based on aUTP task management request stored in the register 420. Besides, othercomponents defined in the JEDEC UFS standards are illustrated in FIG. 8. For example, host controller capabilities, interrupt and host status,UFS interconnect (UIC) command, and vendor specific may be stored in theregister 420.

The embodiments of the present disclosure are not limited to theconfiguration shown in FIG. 8 . In an embodiment, at least some of theinformation stored in the host memory 410 in FIG. 8 may be stored in theregister 420. In an embodiment, at least one of the UTP transfer requestdescriptor, the UPIU information, the PRDT information, and the UTP taskmanagement request list may be stored in the register 420. Further, inanother embodiment, the host memory 410 may include only data buffers,and the remaining information may be stored in the register 420.

FIGS. 9A and 9B are block diagrams of the comparison of the accessfrequency to a host memory between a typical case and an embodiment ofthe disclosure. FIGS. 9A and 9B show examples in which a host operatesaccording to a packet received from a storage device.

FIG. 9A shows an example in which a packet complying with a typicalformat is processed. Referring to FIG. 9A, at least one UTP transferrequest may be stored in the register 420 within a host controller. Forexample, a first transfer request “TRANSFER REQUEST 0” may correspond toa data write request and a third transfer request “TRANSFER REQUEST 2”may correspond to a data read request. The host controller may receivean RTT UPIU from the storage device in response to the first transferrequest “TRANSFER REQUEST 0”. The host controller may also receive adata_in UPIU from the storage device in response to the third transferrequest “TRANSFER REQUEST 2”.

A header region storing header information may be included in a packettransmitted from the storage device. Header information of the RTT UPIUmay include information about the size and offset of data to betransferred for a data write operation. The host controller may performa processing operation using at least some information values in theheader information of the RTT UPIU. For example, the host controllerrefers to logical unit number (LUN) and tag (i.e., identifier)information within the header information of the RTT UPIU and accessesthe host memory 410 to check a corresponding UTP transfer requestdescriptor. The host controller also accesses a location detected fromthe UTP transfer request descriptor in the host memory 410 to check PRDTinformation. The host controller may also access a data buffer based onthe PRDT information (e.g., a buffer address) and transmit data storedin the data buffer to the storage device.

When the data_in UPIU is received, the host controller may access thehost memory 410 to check a UTP transfer request descriptor correspondingto the header information of the data_in UPIU {circle around (1)}. Thehost controller may also access the host memory 410 to checkcorresponding PRDT information {circle around (2)}. Read data includedin the data_in UPIU may be stored in a data buffer corresponding to thePRDT information {circle around (3)}.

According to the above-described method, the host memory 410 isrelatively frequently accessed for a data processing operation. Forinstance, the host controller accesses the host memory 410 twice tocheck a transfer request descriptor and PRDT information and once toread write data to process an RTT UPIU. A total of three accesses to thehost memory 410 are required. At this time, since the host controllerhas lower access priority to the host memory 410 than other elements(e.g., a display I/F, a camera I/F, and a modem) of the host, overheadof data processing is increased.

According to an embodiment of the disclosure, as shown in FIG. 9B, ahost may transmit the first transfer request “TRANSFER REQUEST 0” to astorage device and receive an RTT UPIU responding to the first transferrequest “TRANSFER REQUEST 0” {circle around (1)}. The host may parse abuffer address from the RTT UPIU and may transmit data stored in a databuffer indicated by the buffer address to the storage device {circlearound (2)}. In other words, an access to the host memory 410 performedby a host controller to check PRDT information upon receiving the RTTUPIU may be eliminated.

Similarly, when the host receives a data_in UPIU, the host controllerdoes not need to perform an access operation to check PRDT informationin the host memory 410 in order to determine a location of a data bufferin which read data will be stored. For example, the host controller maydetermine the kind of a request by checking a UTP transfer requestdescriptor based on the header information of the data_in UPIU {circlearound (1)} and may store read data in a data buffer indicated by abuffer address parsed from the data_in UPIU {circle around (2)}.

According to the embodiment described above, the access frequency to thehost memory 410 is decreased, and therefore, data throughput isincreased. For example, in a data write operation, a plurality of RTTUPIUs may be sequentially transmitted to the host in response to asingle command UPIU according to a data write unit in the storagedevice. At this time, data processing may be performed, withoutaccessing the host memory 410 to separately check PRDT information inresponse to each RTT UPIU.

FIG. 10 and FIGS. 11A and 11B are diagrams of a data read operation andpackets involved in a UFS interface, according to an embodiment of thedisclosure.

Referring to FIG. 10 , a command (CMD) UPIU for a data read request maybe transmitted from a host to a storage device. A buffer address (or aphysical address (PA) of a data buffer) may be included in the CMD UPIUfor the data read request. The storage device may read data from amemory core in response to the CMD UPIU for the data read request andmay transmit a data_in UPIU to the host. At this time, the data_in UPIUincludes the PA parsed from the CMD UPIU and the read data. In addition,the storage device may transmit a response UPIU, which indicatescompletion of an operation corresponding to the CMD UPIU, to the host.As described above, the host may store the read data in a data buffer ata location indicated by the PA parsed from the data_in UPIU.

A packet structure of the CMD UPIU may be implemented as shown in FIG.11A and a packet structure of the data_in UPIU may be implemented asshown in FIG. 11B. FIGS. 11A and 11B show examples in which a bufferaddress is included in an existing header region. FIG. 11A shows thestructure of the CMD UPIU and FIG. 11B shows the structure of thedata_in UPIU.

Referring to FIG. 11A, a header region H of the CMD UPIU may include areserved region and a buffer address and relevant information may beincluded in part of the reserved region. For example, a host memorybuffer address may be included in the reserved region. Information CWAindicating that the buffer address is included in the CMD UPIU andinformation CWA_LENGTH indicating the size of a region in which thebuffer address is stored (or the size of a region in which the bufferaddress and the relevant information are stored) may also be included inthe reserved region.

Referring to FIG. 11B, the data_in UPIU may include the header region Hand a payload region DATA including data. The header region H mayinclude a reserved region. A host memory buffer address and relevantinformation may be included in at least part of the reserved region.Information included in the reserved region illustrated in FIG. 11B isthe same as or similar to that illustrated in FIG. 11A. Thus, detaileddescriptions thereof will be omitted.

FIGS. 12 and 13 are diagrams of a data write operation and packetsinvolved in the UFS interface, according to an embodiment of thedisclosure.

Referring to FIG. 12 , a CMD UPIU for a data write request may betransmitted from a host to a storage device. A PA indicating a locationof a data buffer in which write data has been stored in the host may beincluded in the CMD UPIU. The storage device may transmit at least oneRTT UPIU, which indicates that it is ready to receive the write data, tothe host in response to the CMD UPIU for the data write request.According to the size of the write data and a data write unit of thestorage device, a plurality of RTT UPIUs may be transmitted to the host.

For example, a first RTT UPIU, i.e., RTT UPIU_1, may be transmitted fromthe storage device to the host. A first PA PA_1 indicating a location ofa data buffer in which write unit data to be transferred first has beenstored may be included in the RTT UPIU_1. The host may determine thelocation of the data buffer therewithin using the first PA PA_1 parsedfrom the RTT UPIU_1 and may transmit data stored in the data buffer tothe storage device as write data. The host may transmit a data_out UPIUincluding the write data to the storage device.

In addition, the storage device may transmit a second RTT UPIU, i.e.,RTT UPIU_2, to the host. A second PA PA_2 indicating a location of adata buffer in which write unit data to be transferred second has beenstored may be included in the RTT UPIU_2. The host may parse the secondPA PA_2 from the RTT UPIU_2 and may transmit data, which has been storedin a data buffer at the location indicated by the second PA PA_2, to thestorage device. As such operation is repeated, all of the data requestedto be written may be transmitted to the storage device. When the datawriting is completed, the storage device may transmit a response UPIU,which indicates completion of an operation corresponding to the CMDUPIU, to the host.

FIG. 13 shows an example of the packet structure of the above-describedRTT UPIU. In this example, a buffer address is included in an existingheader region. FIG. 13 shows the RTT UPIU_1 among the plurality of RTTUPIUs transmitted in response to a single CMD UPIU. The structure of theother RTT UPIUs may be the same as or similar to that shown in FIG. 13 .

Referring to FIG. 13 , the header region H of the RTT UPIU_1 may includea reserved region. A buffer address indicating a location of a databuffer in which write unit data has been stored may be included in atleast part of the reserved region. The information CWA indicating thatthe buffer address is included and the information CWA_LENGTH indicatingthe size of a region, in which the buffer address is stored, may also beincluded in the reserved region. After the transmission of the RTTUPIU_1 is completed, the next RTT UPIU, e.g., the RTT UPIU_2, may betransmitted to the host. At this time, a value of the buffer addressindicating a location of a data buffer in which write data has beenstored may be changed.

FIG. 14 is a diagram of an example in which an embodiment of thedisclosure is applied to various types of packets defined in the UFSinterface.

A host may sequentially transmit a plurality of UPIUs to a storagedevice. In the example shown in FIG. 14 , a CMD UPIU for a writerequest, i.e., CMD UPIU 1, CMD UPIUs for a read request, i.e., CMD UPIU2, CMD UPIU 4, CMD UPIU 5, and CMD UPIU 6, and a UPIU for a taskmanagement request, i.e., TMF_REQ UPIU 3 are transferred. As describedabove, in the UFS interface, an access to a data buffer in the host isrequired during data write and read operations on the storage device.Accordingly, a buffer address, i.e., a PA, may be included in each ofthe CMD UPIUs, i.e., CMD UPIU 1, CMD UPIU 2, CMD UPIU 4, CMD UPIU 5, andCMD UPIU 6. The storage device may parse the buffer address, i.e., thePA, from each of the CMD UPIUs, i.e., CMD UPIU 1, CMD UPIU 2, CMD UPIU4, CMD UPIU 5, and CMD UPIU 6, and may store and manage the PA.

The storage device may also generate a UPIU in response to a requestreceived from the host and transmit the UPIU to the host. One or moreRTT UPIUs, i.e., RTT UPIU(1)_0 and RTT UPIU(1)_1, and a data_in UPIU,i.e., DATA_IN UPIU(2), including read data are shown in FIG. 14 . Sincean access to a data buffer is required in the host during an operationresponding to an RTT UPIU or a data_in UPIU, a PA may be included ineach of the RTT UPIU and the data_in UPIU.

The host may transmit a UPIU including write data, i.e. DATA_OUTUPIU(1)_0, to the storage device in response to the RTT UPIU. The hostmay also transmit a task management request UPIU, i.e., TMF_REQ UPIU 3,to the storage device. The storage device may perform a managementoperation on commands stored therein in response to the TMF_REQ UPIU 3.The storage device may also transmit a task management response UPIU,i.e., TMF_RESP UPIU(3), indicating the completion of the commandmanagement operation to the host in response to the TMF_REQ UPIU 3.

As described above, a data_out UPIU and a TMF_REQ UPIU from the host anda TMF_RESP UPIU from the storage device are irrelevant to an operationof accessing a data buffer within the host. Such a buffer address asdescribed above may not be included in these UPIUs. Accordingly, as forvarious types of packets transferred through the UFS interface, the sizeof some types of packets excluding a payload may be different from thesize of other types of packets excluding a payload.

FIG. 15 is a block diagram of a storage controller managing a bufferaddress according to an embodiment of the disclosure.

Referring to FIG. 15 , the storage controller 500 may include a controlcircuit 510, a host I/F 520, a memory I/F 530, a CMD queue 541, anaddress (ADD) queue 542, and a data buffer 550. In describing theoperations of the storage controller 500 shown in FIG. 15 , descriptionsof the operations the same as or similar to those described withreference to FIG. 3 will be omitted. The data buffer 550 may temporarilystore write data DATA_W and read data DATA_R.

The control circuit 510 may include various elements for controllingdata write and read operations on a memory core according to a UFSinterface protocol. The control circuit 510 may include a hostcontroller 511. The host controller 511 may include a packet determiner511_1. The host controller 511 may also include a UTP engine (not shown)for UTP process. The host controller 511 may generate a packet or parsevarious kinds of information from a received packet, as described above.

A parsed command and buffer address CMD/ADD_Buf may be stored andmanaged in the CMD queue 541 and the ADD queue 542 based on the controlof the control circuit 510. A buffer address ADD_Buf may be read fromthe ADD queue 542 and provided to the host controller 511 and a packetcontaining the buffer address ADD_Buf may be generated. The packetdeterminer 511_1 may determine whether a packet to be transmitted to ahost is of a type requiring an access to a data buffer of a host memory.According to the determination result, the ADD queue 542 may beselectively accessed

FIG. 16 is a flowchart of a method of operating the storage controller500 illustrated in FIG. 15 , according to an embodiment of thedisclosure.

Referring to FIG. 16 , as described above, a storage device parses abuffer address from packets transmitted from a host and stores andmanages the buffer address in operation S41.

Thereafter, the storage device performs processes corresponding to aplurality of requests transmitted from the host and transmits packetsresulting from the processes to the host. When generating the packetsaccording to the processing result, the storage device detects the typeof a packet to be generated in operation S42 and determines whether thepacket to be generated requires an access to a data buffer in the hostbased on the detection result in operation S43.

When it is determined that the packet does not require an access to adata buffer in the host, the packet may be generated without accessinginformation in an address queue within the storage device. However, whenit is determined that the packet requires an access to a data buffer inthe host, a buffer address may be read from the address queue in thestorage device in operation S44 and a packet containing the bufferaddress may be generated and transmitted to the host in operation S45.

FIGS. 17A through 17C are block diagrams of the operation of a storagesystem when a plurality of RTT UPIUs are transmitted in response to asingle command UPIU. FIGS. 17A through 17C show an example when four RTTUPIUs are transmitted in response to a single command UPIU.

Referring to FIG. 17A, a storage system 600A may include a host 610A anda storage device 620A. The host 610A may include a host controller 611A.The host controller 611A may include an address calculator 611A_1. Thestorage device 620A may include a storage controller 621A and a memorycore 622A.

A buffer address ADD_Buf 1 indicating a location of a data buffer inwhich write data has been stored may be included in a CMD UPIU. Thestorage system 600A may include the buffer address ADD_Buf 1 in each offour RTT UPIUs, i.e., RTT UPIU_1 through RTT UPIU_4. Locations ofrespective data buffers in which write data respectively correspondingto the four RTT UPIUs, i.e., RTT UPIU_1 through RTT UPIU_4, have beenstored may be different from one another and the address calculator611A_1 may calculate buffer addresses ADD_Buf 1_1 through ADD_Buf 1_4respectively indicating the data buffers corresponding to the four RTTUPIUs, i.e., RTT UPIU_1 through RTT UPIU_4, from the buffer addressADD_Buf 1. The calculation may be performed using the headerinformation, which has been described above, together with the bufferaddress ADD_Buf 1 included in the RTT UPIUs.

FIG. 17B shows an example in which the above-described addresscalculation is performed in a storage device. Referring to FIG. 17B, astorage system 600B may include a host 610B and a storage device 620B.The host 610B may include a host controller 611B. The storage device620B may include a storage controller 621B and a memory core 622B. Thestorage controller 621B may include an address calculator 621B_1.

The storage controller 621B may receive a CMD UPIU containing the bufferaddress ADD_Buf 1 and may sequentially transmit four RTT UPIUs, i.e.,RTT UPIU_1 through RTT UPIU_4, to the host 610B, taking a write unitinto account. The address calculator 621B_1 in the storage controller621B may calculate the buffer addresses ADD_Buf 1_1 through ADD_Buf 1_4using the size of the write unit and the buffer address ADD_Buf 1 whichhas been parsed. The first buffer address ADD_Buf 1_1 may be included inthe first RTT UPIU, i.e., RTT UPIU_1, and the fourth buffer addressADD_Buf 1_4 may be included in the fourth RTT UPIU, i.e., RTT UPIU_4.

FIG. 17C shows an example in which a host transmits a plurality ofbuffer addresses to a storage device, taking the size of a write unitinto account. Referring to FIG. 17C, a storage system 600C may include ahost 610C and a storage device 620C. The host 610C may include a hostcontroller 611C. The storage device 620C may include a storagecontroller 621C and a memory core 622C.

The host 610C may include a plurality of buffer addresses, i.e., ADD_Buf1_1 through ADD_Buf 1_4, in a single CMD UPIU, taking the size of awrite unit of the storage device 620C into account. The storage device620C may store and manage the plurality of the buffer addresses ADD_Buf1_1 through ADD_Buf 1_4 which have been received.

The storage device 620C may also sequentially transmit four RTT UPIUs,i.e., RTT UPIU_1 through RTT UPIU_4, to the host 610C and may include adifferent buffer address in each of the RTT UPIUs. For example, thefirst buffer address ADD_Buf 1_1 may be included in the first RTT UPIU,i.e., RTT UPIU_1, and the fourth buffer address ADD_Buf 1_4 may beincluded in the fourth RTT UPIU, i.e., RTT UPIU_4.

FIGS. 18A and 18B illustrate structures of a packet according to someembodiments of the disclosure. FIG. 18A shows a first type packetcontaining a buffer address, and FIG. 18B shows a second type packet notcontaining a buffer address. Here, the buffer address is included in anextra header segment EHS.

Referring to FIG. 18A, the first type packet may include the header H,the extra header segment EHS, and a payload. Various kinds of headerinformation may be included in the header H. A buffer addresscorresponding to a PA of a buffer address in a host memory may beincluded in the extra header segment EHS. Besides the buffer address,other various kinds of information for data management in a storagedevice may also be included in the extra header segment EHS.

In case of a UFS interface, the header H of a packet may have apredetermined size. For example, the header H may have a size of 32bytes. The header H may include fields of various kinds of information,such as a LUN, a tag, flags, and a command set type. The size of theextra header segment EHS may vary and information about the size of theextra header segment EHS may be included in one of the fields in theheader H. In an embodiment illustrated by FIG. 18A, the extra headersegment EHS of the first type packet has a size of a byte(s).

In FIG. 18B, the extra header segment EHS is not included in the secondtype packet. Accordingly, the size of the second type packet excluding apayload may be fixed to 32 bytes. However, the size of the first typepacket excluding a payload may be greater than 32 bytes and vary.Therefore, the size of a packet excluding a payload may vary with thetype of packet in some embodiments of the disclosure.

FIGS. 19 through 25 are diagrams of various structures of a packetgenerated according to some embodiments of the disclosure. It is assumedthat a buffer address is included in the extra header segment EHS of apacket. Various fields collectively referred to as an EHS field may beincluded in the extra header segment EHS. The EHS field may include anEHS header field and an EHS data field.

FIG. 19 shows a CMD UPIU for a data write operation in an embodiment ofthe disclosure. As shown in FIG. 19 , the CMD UPIU may include theheader region H and the extra header segment EHS. The header region Hmay include information about a total EHS length and may also includeinformation about an expected data transfer length.

The extra header segment EHS may include EHS type information EHS_TYPEand EHS length information EHS_LENGTH. The EHS type information EHS_TYPEmay be set to a value which varies. When the EHS type informationEHS_TYPE is set to a particular value, e.g., 2 h, it may indicate that abuffer address has been included in the extra header segment EHS. In theembodiment shown in FIG. 19 , a buffer address corresponding to a PA ofa data buffer in which write data has been stored is “0x40C0_0000”.

FIGS. 20A and 20B show examples of RTT UPIUs corresponding to the CMDUPIU shown in FIG. 19 . FIG. 20A shows the first RTT UPIU, i.e., RTTUPIU_1, and FIG. 20B shows the second RTT UPIU, i.e., RTT UPIU_2.Although not shown, more RTT UPIUs may be transmitted from a storagedevice to a host according to the size of a write unit.

Referring to FIGS. 20A and 20B, each of the first and second RTT UPIUs,i.e., RTT UPIU_1 and RTT UPIU_2, may include the header region H and theextra header segment EHS. The header region H may include a data bufferoffset and data transfer counter information. The extra header segmentsEHS of the respective first and second RTT UPIUs, i.e., RTT UPIU_1 andRTT UPIU_2, may include the same value, e.g., “0x40C0_0000” for a bufferaddress.

The host may determine the location of a data buffer storing the writedata using information in the header region H and the extra headersegment EHS included in each of the first and second RTT UPIUs, i.e.,RTT UPIU_1 and RTT UPIU_2. For example, the host may determine thelocation of the data buffer using the data buffer offset, the datatransfer counter information, and the buffer address and may transmitcorresponding write data to the storage device.

FIGS. 21A and 21B show other examples of RTT UPIUs corresponding to theCMD UPIU shown in FIG. 19 . FIG. 21A shows the first RTT UPIU, i.e., RTTUPIU_1, and FIG. 21B shows the second RTT UPIU, i.e., RTT UPIU_2.Redundant descriptions the same as those explained above with referenceto FIGS. 20A and 20B will be omitted.

Referring to FIG. 19 and FIGS. 21A and 21B, a storage device maycalculate a plurality of buffer addresses using a buffer address (e.g.,0x40C0_0000) contained in a CMD UPIU and may include the bufferaddresses in a plurality of RTT UPIUs, respectively. Buffer addresseshaving different values may be included in a plurality of RTT UPIUs. Forexample, a buffer address corresponding to 0x40C0_0000 may be includedin the first RTT UPIU, i.e., RTT UPIU_1, and a buffer addresscorresponding to 0x40C0_8000 may be included in the second RTT UPIU,i.e., RTT UPIU_2. According to embodiments show in FIGS. 21A and 21B, ahost may directly access a data buffer at the location indicated by abuffer address contained in an RTT UPIU, without performing acalculation operation on the buffer address contained in the RTT UPIU.

FIGS. 22 through 25 show examples in which a host includes a pluralityof buffer addresses in a single CMD UPIU. Embodiments illustrated inFIGS. 22 through 25 may be applied when a plurality of write units ofdata requested to be written are continuously or discontinuously locatedin a buffer area. It would be more efficient to apply the embodiments tocases where write units of data are discontinuously located in a bufferarea. The structure and information of a header region used in theembodiments described with reference to FIGS. 22 through 25 are the sameas or similar to those described above and thus not illustrated in FIGS.22 through 25 .

Referring to FIG. 22 , an EHS field included in a CMD UPIU may includean EHS header and an EHS data. The EHS header may include the typeinformation EHS_TYPE and the length information EHS_LENGTH, as describedabove. When data corresponding to the size of a write unit istransmitted four times from the host to a storage device in response toa single CMD UPIU, buffer addresses, i.e., BUFFER ADDRESS1_1 throughBUFFER ADDRESS1_4, at which four data having the size of the write unitare respectively located, may be included in the EHS field. The storagedevice may store and manage the buffer addresses, i.e., BUFFERADDRESS1_1 through BUFFER ADDRESS1_4.

FIGS. 23A and 23B show RTT UPIUs transmitted by a storage device. FIG.23A shows the first RTT UPIU, i.e., RTT UPIU_1, and FIG. 23B shows thefourth RTT UPIU, i.e., RTT UPIU_4. Referring to FIG. 23A, an EHS fieldof the first RTT UPIU, i.e., RTT UPIU_1, may contain the first bufferaddress, i.e., BUFFER ADDRESS1_1. The host may parse the first bufferaddress, i.e., BUFFER ADDRESS1_1, from the first RTT UPIU, i.e., RTTUPIU_1, and may transmit data, which has the size of a write unit andcorresponds to the first buffer address, i.e., BUFFER ADDRESS1_1, to thestorage device. Referring to FIG. 23B, an EHS field of the fourth RTTUPIU, i.e., RTT UPIU_4, may contain the fourth buffer address, i.e.,BUFFER ADDRESS1_4, having a different value than the first bufferaddress, i.e., BUFFER ADDRESS1_1. A host may transmit data correspondingto the fourth buffer address, i.e., BUFFER ADDRESS1_4, to the storagedevice.

FIG. 24 shows a modifiable embodiment in which an RTT UPIU containsfirst through fourth buffer addresses, i.e., BUFFER ADDRESS1_1 throughBUFFER ADDRESS1_4. All of the first through fourth buffer addresses,i.e., BUFFER ADDRESS1_1 through BUFFER ADDRESS1_4, may be included ineach of the first through fourth RTT UPIUs, i.e., RTT UPIU_1 through RTTUPIU_4. The host may access data selectively using one of the bufferaddresses according to information in the header.

FIG. 25 shows an example of a data_in UPIU. It is assumed that the CMDUPIU shown in FIG. 22 requests a read operation.

The storage device may store and manage a plurality of buffer addresses,i.e., BUFFER ADDRESS1_1 through BUFFER ADDRESS1_4, contained in a CMDUPIU corresponding to a read request. When transmitting a data_in UPIUin response to the CMD UPIU, the storage device may include the bufferaddresses, i.e., BUFFER ADDRESS1_1 through BUFFER ADDRESS1_4, in thedata_in UPIU. The host may store read data at corresponding locations ofdata buffers in a host memory using the buffer addresses, i.e., BUFFERADDRESS1_1 through BUFFER ADDRESS1_4, contained in the data_in UPIU.

According to the embodiments of the disclosure, a buffer addressindicating a location of a data buffer in a host is transferred betweenthe host and a storage device, and therefore, a read operation performedby a host memory to determine the location of the data buffer needed tobe accessed can be eliminated. As a result, overhead of data processingbetween the host and the storage device is reduced and data processingperformance is increased.

As is traditional in the field, embodiments may be described andillustrated in terms of blocks which carry out a described function orfunctions. These blocks, which may be referred to herein as units ormodules or the like, are physically implemented by analog and/or digitalcircuits such as logic gates, integrated circuits, microprocessors,microcontrollers, memory circuits, passive electronic components, activeelectronic components, optical components, hardwired circuits and thelike, and may optionally be driven by firmware and/or software. Thecircuits may, for example, be embodied in one or more semiconductorchips, or on substrate supports such as printed circuit boards and thelike. The circuits constituting a block may be implemented by dedicatedhardware, or by a processor (e.g., one or more programmedmicroprocessors and associated circuitry), or by a combination ofdedicated hardware to perform some functions of the block and aprocessor to perform other functions of the block. Each block of theembodiments may be physically separated into two or more interacting anddiscrete blocks without departing from the scope of the disclosure.Likewise, the blocks of the embodiments may be physically combined intomore complex blocks without departing from the scope of the disclosure.

While the disclosure has been particularly shown and described withreference to embodiments thereof, it will be understood that variouschanges in form and details may be made therein without departing fromthe spirit and scope of the following claims.

What is claimed is:
 1. A storage device comprising: a nonvolatilememory; and a controller coupled to the nonvolatile memory, wherein thecontroller is configured to: receive a first command and a first addressfrom an external device, transmit first data corresponding to the firstcommand and the first address to the external device, receive a secondcommand and a second address from the external device, and transmit thesecond address and a request for second data corresponding to the secondcommand to the external device.
 2. The storage device of claim 1,wherein the first command is a read command, and the second command is awrite command.
 3. The storage device of claim 2, wherein the first datais read from the nonvolatile memory.
 4. The storage device of claim 2,wherein the controller is further configured to: receive the second datafrom the external device, and store the second data in the nonvolatilememory.
 5. The storage device of claim 1, wherein the first addressindicates a first location of a data buffer in the external device inwhich the first data is to be stored, and the second address indicates asecond location of the data buffer in the external device in which thesecond data is stored.
 6. The storage device of claim 1, wherein thestorage device is an embedded multi-media card (eMMC) or an embeddeduniversal flash storage (UFS) memory device.
 7. The storage device ofclaim 1, wherein the controller is further configured to communicatewith the external device via a universal flash storage (UFS) interface.8. The storage device of claim 1, wherein the first command and thefirst address are included in a first packet that is a UFS protocolinformation unit (UPIU).
 9. A storage device comprising: a nonvolatilememory; and a controller coupled to the nonvolatile memory, wherein thecontroller is configured to: receive a first packet including a readcommand and a first address from an external device, read first datastored in the nonvolatile memory, and transmit a second packet includingthe first address and the first data corresponding to the read commandto the external device, wherein the controller communicates with theexternal device via a universal flash storage (UFS) interface, and eachof the first packet and the second packet is a UFS protocol informationunit (UPIU).
 10. The storage device of claim 9, wherein the firstaddress indicates a first location of a data buffer in the externaldevice in which the first data is to be stored.
 11. The storage deviceof claim 9, wherein the controller is further configured to: receive athird packet including a write command and a second address from theexternal device, and transmit a fourth packet including the secondaddress and a request for second data corresponding to the write commandto the external device.
 12. The storage device of claim 11, wherein thesecond address indicates a second location of a data buffer in theexternal device in which the second data is stored.
 13. The storagedevice of claim 9, wherein the storage device is an embedded multi-mediacard (eMMC) or an embedded universal flash storage (UFS) memory device.14. The storage device of claim 9, wherein the controller is furtherconfigured to control a data write operation and a data read operationon the nonvolatile memory according to a UFS interface protocol.
 15. Astorage device comprising: a nonvolatile memory; and a controllercoupled to the nonvolatile memory, wherein the controller is configuredto: receive a first packet including a write command and a first addressfrom an external device, and transmit a second packet including thefirst address and a request for first data corresponding to the writecommand to the external device, wherein the controller communicates withthe external device via a universal flash storage (UFS) interface, andwherein each of the first packet and the second packet is a UFS protocolinformation unit (UPIU).
 16. The storage device of claim 15, wherein thefirst address indicates a first location of a data buffer in theexternal device in which the first data is stored.
 17. The storagedevice of claim 15, wherein the controller is further configured to:receive a third packet including a read command and a second addressfrom the external device, read second data stored in the nonvolatilememory, and transmit a fourth packet including the second address andthe second data corresponding to the read command to the externaldevice.
 18. The storage device of claim 17, wherein the second addressindicates a second location of a data buffer in the external device inwhich the second data is to be stored.
 19. The storage device of claim15, wherein the storage device is an embedded multi-media card (eMMC) oran embedded universal flash storage (UFS) memory device.
 20. The storagedevice of claim 15, wherein the controller is further configured tocontrol a data write operation and a data read operation on thenonvolatile memory according to a UFS interface protocol.